Blog

Gavin Pickin

May 13, 2022

Spread the word


Share your thoughts

We were busy this week, we released a lot of content for you... on the podcast, cfcasts, youtube, and our blog. Here's the summary in bite size pieces

Podcast

CFCasts

YouTube

Online CF Meetup

  • Code Reuse in CF: Is Spaghetti Code still Spaghetti if it's DRY? with Gavin Pickin--CF Meetup #295 Find out the difference between DRY code and WET code, and what one is better, and more importantly, WHY. We write code one, but we read it over and over again, maintaining our code is 90% of the job... code reuse is our friend. You are already Re-using code, even if you didn't know you were. We'll learn about the different types of Code Reuse in ColdFusion, the pros and cons of each. https://www.youtube.com/watch?v=MnOW6G5MVqE

Ortus Solutions Blog

Add Your Comment

Recent Entries

ColdBox 8.2.0: Middleware, Streaming, AI Gateways, and a Whole Lot More

ColdBox 8.2.0: Middleware, Streaming, AI Gateways, and a Whole Lot More

ColdBox 8.2.0 is the result of work we started in March. Several of its headline features, including route-scoped middleware and Server-Sent Events, were incubated for months before shipping. We held them back on purpose: we wanted the APIs settled, the edge cases covered, and the testing story complete before asking you to build on them. They're ready now.

Luis Majano
Luis Majano
September 23, 2026
Assert Like You Mean It, TestBox 7.1 Part 1: Set Expectations

Assert Like You Mean It, TestBox 7.1 Part 1: Set Expectations

If you have ever tested that two collections contain "the same stuff, order doesn't matter," you already know the workaround: sort both arrays, compare them element by element, and hope nobody adds a duplicate. It works, but it isn't what you meant to write. You meant "these are the same set."

Luis Majano
Luis Majano
September 23, 2026
Is Your QA Process Ready for Your Next ColdFusion or BoxLang Release?

Is Your QA Process Ready for Your Next ColdFusion or BoxLang Release?

As applications continue to evolve, QA can easily become reactive. Teams may test late in the development process, focus only on happy-path scenarios, repeat manual checks, or rely on AI-generated changes without fully validating the results. ​ These gaps can create risks that are not always visible until they affect users, disrupt operations, or require costly fixes in production.

Maria Jose Herrera
Maria Jose Herrera
September 21, 2026